Skip to content

feat(lazurio): Buddy's project beside the Lazurio Folder, made only by the server and unlisted in Chat - #214

Merged
immakermatty merged 9 commits into
mainfrom
lazurio/buddy-project-beside-folder
Nov 17, 2026
Merged

immakermatty merged 9 commits into
mainfrom
lazurio/buddy-project-beside-folder

Conversation

@immakermatty

Copy link
Copy Markdown

Status: ready for review. It ships on its own: without T3CODE_LAZURIO_BUDDY_FOLDER every path behaves as on main.

Problem

A managed Environment (T3CODE_LAZURIO_FOLDER) takes exactly one project, the Lazurio Folder. Buddy's next generation (plan LZD-0033, pilot R1) is meant to be an ordinary T3 Code thread in a project over a Buddy folder beside the Folder, in the same server as Chat. Today the overlay refuses that in four places, so the pilot cannot start:

  • guardProjects refuses every project whose root is not the Folder (project_mutation_failed, "In this Environment, the Lazurio project is the Lazurio Folder itself.").
  • guardCommands refuses thread.create, messages and forks outside the Folder project's root.
  • guardTurns refuses to open an agent session whose cwd is not the Folder.
  • The web sends every new thread to the Folder's project and offers no other project in the palette.

Why the rule exists and what stands on it

The rule makes the Folder the entry context of every chat (F51): agents start where the Folder's instructions, manual and organisations are, not in a stray repository. Several things rely on the Folder being the only project:

  • Default project. The first run waits for the Folder's project, and a new thread from the sidebar, the palette or t3_thread_launch lands there. Archiving it is refused because a managed Environment would then only offer "Add project", which it refuses.
  • Default model. The Platform's recommended model is written as the Folder project's own override (projectSettingsOverrides[<folder project>]), tracked in lazurio/model-recommendation.json; the route accepts only the Folder's path.
  • Scratch and triage. No Scratch folder and no triage, so nothing creates a project outside the Folder behind the guards' back.
  • Buddy's current server (T3CODE_LAZURIO_BUDDY=1) uses the same managed-Folder mechanism with its own Folder (~/Lazurio/.agents/buddy); its guards key off that switch and the provider instance buddy.
  • Launchpad links to Chat, not to a project; nothing there depends on the project list.

Fix

The exception is narrow and not a Chat feature: Buddy's project is Lazurio's own.

  • T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder: absolute, existing, canonical, only together with T3CODE_LAZURIO_FOLDER, and neither inside the Folder nor around it (managedFolderConfig.ts).
  • Only the server's startup makes the project: ensureManagedFolderProject also bootstraps Buddy's project (title Buddy) through ProjectService.bootstrap, which no client, agent or CLI reaches. create (t3 project add, t3_project_create, the web) still accepts only the Folder, and renaming, archiving or deleting Buddy's project is refused.
  • Threads, messages, forks and agent turns run in the root of Buddy's folder as in the Folder's; worktrees stay refused.
  • The model recommendation stays the Folder project's alone, so a model set for Buddy's project is never overwritten.
  • The server sends lazurioBuddyFolder to clients (server.getConfig). The web leaves the project out of every project list and its threads, with their subagents and tasks, out of the sidebar, the palette and thread search. Unlike tag-hidden threads, a direct link /<environment>/<thread> still opens it. The logic is in the overlay module packages/client-runtime/src/lazurio/unlistedProjects.ts; projectEntities.ts, threadShell.ts and apps/web/src/state/threads.ts carry one hook each and join the allowlist.

Why a variable and not a fixed sibling folder

A variable follows the pattern of T3CODE_LAZURIO_FOLDER: Machines already declares the Folder in the service's environment, and conversion to the new Buddy goes person by person. A fixed sibling Buddy would switch the project on for anyone who happens to have such a folder, could not be turned on or off from the Platform or Machines per person, and would tie the server to a home-directory layout it does not own. Without the variable nothing changes.

What this does not do

Agents in Chat still see Buddy's thread through MCP (t3_thread_list, t3_project_list); the server hides nothing, because Buddy has to see Chat's threads and the server cannot yet tell the two apart. The official desktop and mobile apps list the project as an ordinary one, since unlisting lives in the web client. Buddy's own window over the thread, model choice in that window, server-side unlisting and the end of the second server are a later step (R3). This change makes that step easier: the server and the web already know which project is Buddy's (lazurioBuddyFolder, unlistedProjectIdsAtom), so R3 can bind Buddy's guards to that project instead of the server-wide switch.

Verification

  • vp test run for managedFolderGuards, managedFolderConfig, managedFolderStartup, managedFolder, modelRecommendation, managedFolderVcs (server) and unlistedProjects, threadShell, projectEntities, threadTagFilter (client-runtime): all pass. New cases: the config (beside, needs the Folder, not inside or around it), the project guard (create refused, bootstrap through a symlink canonicalised, rename, archive and delete refused), commands and turns in Buddy's folder with and without the variable, startup creates both projects once and keeps the recommendation record on the Folder's project, a model override on another project survives the recommendation, and the client lists.
  • node --test scripts/lazurio-release-contract.test.mjs: 52 pass. The seam now pins bootstrap through inFolderOrBuddy and create through inFolder.
  • vp run check:changed: format, lint, knip, graphql, typecheck and React compiler pass. Its test step fails only in apps/server/src/provider/AgentContextBudget.test.ts, which fails the same way on main (cf662620) and is Agent context budget test fails on current main #167; this change does not touch agent context.
  • Live run on a dev server with separate data (--home-dir, a clean environment, a test Folder and Buddy folder):
    • the startup created both projects; t3 project add of another folder was refused as before;
    • t3 thread start in Buddy's folder with Claude Haiku: the agent ran in Buddy's folder, had only Buddy's AGENTS.md and called t3_project_list through the t3-code MCP server (it listed Lazurio and Buddy);
    • in the web client the sidebar, the project filter and thread search (by title and by message text) showed nothing of Buddy's project; the direct link opened its thread with history, a message sent from the composer got its answer, and the sidebar stayed empty meanwhile; a new thread in the Lazurio project was listed as usual.
  • Buddy's current server: its config has no Buddy folder, so every new branch is off; buddySurfaceGuards, buddySurfaceStartup, buddySurfaceThread and cli tests pass (32).

Done by Claude Opus 5.5 in Claude Code.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

🤖 Generated with Claude Code

@immakermatty

Copy link
Copy Markdown
Author

Supervisor: release placement of this change. (2026-11-17)

This goes into a separate patch release, 0.1.9-lazurio.2, right after stable 0.1.9-lazurio.1. It does not wait for the v0.1.10 rebuild (#213).

Do not merge before 0.1.9-lazurio.1 is published. Stable 0.1.9-lazurio.1 is dispatched from cf662620, and the release workflow only accepts the tip of main as its source. If this PR merged first, main would move and stable would have to include code that the Ring 0 canary and the Admin's acceptance never covered. The release owner's approval for this PR therefore counts only after stable is out. Until then this PR may be reviewed, but not merged.

After 0.1.9-lazurio.1 is published:

  1. The PR is merged after a fresh review on its exact head. If main has not moved, no rebase is needed.
  2. 0.1.9-lazurio.2 follows the normal path from the tip of main: preview, Ring 0 canary with a check of this change (with and without T3CODE_LAZURIO_BUDDY_FOLDER: the inner project is created, guarded and kept out of the lists, and a direct thread link opens), the Admin's acceptance, then stable.
  3. The v0.1.10 rebuild (Přestavba na upstream T3 Code v0.1.10 #213) carries this change as its own overlay row.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

@immakermatty

Copy link
Copy Markdown
Author

New head 12c6aac8: a Buddy folder that does not exist yet no longer stops the server. The resolver treats it as "no Buddy project" and the Folder's Chat starts as before; a relative path, a file, or a folder inside or around the Folder still fails the config. Case added to managedFolderConfig.test.ts (5 pass); docs updated.

Release, as agreed with the T3 Release thread above: no merge before stable 0.1.9-lazurio.1; then fresh review on the exact head and 0.1.9-lazurio.2 with its own canary.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

@agentrozjedemeai

Copy link
Copy Markdown
Collaborator

@immakermatty Předávám vám dokončení PR na headu 1ed673990bdbd1c4f59625cc138d999d5c02cc38: dosud chybí nezávislé review a povinné kontroly ještě běží. V mém Prostředí chybí vp a požadovaný Node 26.12.1; pokus o release-contract test skončil před testy kvůli chybějící závislosti effect, takže review ani kontroly zde nejsou dokončené. Zajistěte prosím kompletní nezávislé review tohoto headu včetně předepsaných testů a ověření rozhraní; poté ověřte všechny povinné kontroly, vyřešené konverzace a ostatní pravidla merge. Sloučení je možné až po splnění těchto podmínek.

— Pablo

@agentrozjedemeai agentrozjedemeai removed their assignment Nov 17, 2026

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes.

Blocking

  1. apps/server/src/lazurio/managedFolderConfig.ts:50-52: startsWith("..") also rejects a relative component such as ..buddy as though it were ... With Folder /home/u/Lazurio and Buddy /home/u/Lazurio/..buddy, both containment checks return false, so the nested directory is accepted and the Buddy agent can inherit the Folder's instructions. Compare whole path components (.. or ../…) and test both containment directions, including names beginning with two dots.
  2. packages/client-runtime/src/state/threadShell.ts:634-653: the unlisted keys only reach the three live list atoms. The archive uses hiddenThreadKeysAtom instead (apps/web/src/lib/archivedThreadsState.ts:21-26), so an archived Buddy thread and its project appear in Settings → Archived threads; the PR-linked thread lists also use the tag-only set (apps/web/src/components/pullRequest/PullRequestThreadLinks.tsx:71). Filter the archived snapshots and linked-thread lists by the Buddy project and its descendants as well, without blocking direct links. Cover archived Buddy threads and linked rows in tests.
  3. packages/client-runtime/src/state/threadShell.ts:637-648: environments without an unlisted project are omitted from the traversal. A task delegated from Buddy to a connected environment therefore cannot follow its hidden parent and appears in that environment's lists. Include all enabled environments in the descendant traversal, and test a Buddy parent delegating to another environment.
  4. apps/server/src/lazurio/managedFolderConfig.ts:67 and packages/client-runtime/src/state/projectEntities.ts:47-53: when a previously configured Buddy directory is missing on restart, the config drops its path but the persisted Buddy project and threads remain. The client then treats them as ordinary listed history, contrary to the intended unlisting. Preserve enough identity to keep existing Buddy history unlisted while leaving Chat running, and test the restart with an existing project and absent directory.

Non-blocking

Focused server and client tests passed (60 tests), as did the release contract (52 tests). I did not independently exercise the web client in a browser; the PR describes the author's live run. CI was still running when checked.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

All four blocking findings fixed in c8825883.

  1. Path components. within now treats only .. or ../… as outside, so Lazurio/..buddy counts as inside the Folder and is refused. A sibling named ..Buddy is still beside it, and the check runs in both directions. managedFolderConfig.test.ts covers ..buddy inside the Folder, a Folder under Buddy/..x with Buddy around it, and the ..Buddy sibling. The ..buddy case is accepted on the old head.
  2. Archive and pull request rows.
    • createArchivedThreadSnapshotsAtomFamily takes unlistedProjectIdsAtom and adds the archived threads of Buddy's project to the keys it already hides, so their children follow.
    • The web passes it the new listHiddenThreadKeysAtom (tag-hidden ∪ unlisted), so archived children of the live Buddy thread stay out too. PullRequestThreadLinks.tsx reads the same set.
    • The thread route still reads the tag-only hiddenThreadKeysAtom, so a direct link opens. Tests in lazurio/unlistedProjects.test.ts cover the archived Buddy thread, the archived child of the live one and the linked-row set.
  3. Tasks in other environments. The traversal now gets every enabled environment as soon as one of them has an unlisted project. A test delegates from Buddy's thread to a second environment, and that task leaves the lists.
  4. Missing folder on restart. The config keeps the declared path, absolute but not canonical, when the folder is missing. The startup does not bootstrap there, and the web keeps the earlier project and its threads unlisted. Nothing resolves to that path, so no turn opens there. managedFolderStartup.test.ts restarts over the same database after the folder is removed: Chat starts and the Buddy project is still there.

The new files are on the allowlist (archivedThreads.ts, lib/archivedThreadsState.ts, PullRequestThreadLinks.tsx), and a simulation of the CI gate over the diff comes out clean. The docs are updated.

  • Release contract: 52 pass.
  • check:changed: format, lint, knip, graphql, typecheck and React compiler pass. The test step fails only in AgentContextBudget (Agent context budget test fails on current main #167, the same on main).
  • Focused tests: server 28, client 20.

Please review the exact head c8825883. The release order is unchanged: no merge before stable 0.1.9-lazurio.1. Plan #179 now also has this waiting for D to finish, unless an exception is recorded there.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes.

Blocking

  1. apps/web/src/components/pullRequest/PullRequestThreadLinks.tsx:121 and packages/client-runtime/src/state/threadTagFilter.ts:49: linked rows still reveal an archived Buddy thread. The linked-threads query includes archived records, but listHiddenThreadKeysAtom and loadedThreadRefs contain the live shell only; with the normal tag filter off, visibleLinkedThreads keeps unloaded rows. Filter archived Buddy project rows and descendants as well, and test a linked Buddy thread after archiving it.
  2. packages/client-runtime/src/state/archivedThreads.ts:98-115: when the archive is scoped to a remote environment, an archived task delegated from an archived Buddy thread in another environment is shown. Only the scoped snapshots are traversed, the archived parent is absent from the live hidden set, and hidingAnywhere tracks tag filters rather than unlisted projects. Preserve parent visibility across archive scopes and test this case with tag filtering off.
  3. apps/server/src/lazurio/managedFolderConfig.ts:71-74: the missing-folder fallback uses the declared spelling, while an existing symlink was resolved to its canonical target when the Buddy project was created. If that target is removed and the symlink becomes dangling, restart advertises the link path, which no longer matches the persisted project root, and Buddy history becomes listed again. Preserve the project's canonical identity across this restart and test the symlink case.

Non-blocking

The path-component and live cross-environment fixes address the corresponding earlier findings. Focused tests passed (37), as did the release contract (52). check:changed passed format, lint, knip, GraphQL, typecheck and React compiler; its test stage failed only AgentContextBudget.test.ts, which the PR reports also fails on main (#167). CI was pending. I did not independently exercise the web client in a browser; the PR describes the author's live run.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

All three blocking findings are fixed in 72d18405.

  1. Pull request rows. Each row carries its projectId, so PullRequestThreadLinks.tsx now drops rows of unlisted projects before visibleLinkedThreads. That covers archived Buddy threads and their subagents and side chats, which live in the same project. The filter is apps/web/src/lazurio/unlistedRows.ts, tested with a live and an archived Buddy row.
  2. Archive scoped elsewhere. createArchivedThreadSnapshotsAtomFamily takes unlistedEnvironmentIdsAtom (environments with an unlisted project, wired in the web). Their archives join the single pass but are not returned, so a task archived in another environment follows its archived Buddy parent. The new test scopes the archive to the remote environment with tag filtering off. It fails without the option and passes with it.
  3. Dangling symlink. For a missing Buddy folder the config now follows links, dangling ones too, and canonicalises the deepest existing ancestor. A link whose target was removed therefore still names the target, the root the project was created with. Tested in managedFolderConfig.test.ts.

A known limit I'd rather not fix here: a live task in another environment whose Buddy parent is archived stays listed. The live shell holds no archived parents, rows carry no lineage, and the only client-side answer is upstream's hidingAnywhere. Turning that on would also hide every unloaded linked row and every orphaned task for all Chat threads. Hiding on the server, which knows the lineage, belongs to the later cut (R3), and the docs say so. Buddy is one long thread, so this needs an archived Buddy thread that delegated across environments.

Checks:

  • Release contract: 52 pass.
  • check:changed: format, lint, knip, graphql, typecheck and React compiler pass. The test step fails only in AgentContextBudget (Agent context budget test fails on current main #167).
  • The new web file sits in apps/web/src/lazurio/, so it needs no allowlist entry, and the allowlist check on the diff comes out clean.

Please review the exact head 72d18405, and give a verdict on the limit above.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes.

Blocking

  • packages/client-runtime/src/lazurio/unlistedProjects.ts:44-57: the earlier cross-environment finding remains when Buddy's parent thread is archived while its delegated task is still live. The live shell no longer contains the parent, so inProjects cannot seed its key and the task appears in Chat's lists in the other environment. This violates the stated behavior that Buddy's tasks stay unlisted. Preserve the archived parent's identity for live descendant filtering and add a test for a live remote task with an archived Buddy parent; retain direct-link access and ordinary Chat threads.

Non-blocking

The three findings on the preceding head are addressed. The stated archived-parent limitation remains blocking for the reason above. Focused tests passed (64); the release contract passed (52). I did not independently verify the web client in a browser; the PR records the author's run. CI was still running.

Order and migrations: publish stable 0.1.9-lazurio.1 before merging this PR, as recorded in #214 (comment); the plan's documentation gate must also be complete before implementation proceeds.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Fixed in 10a65501, by removing the state instead of chasing it on the client.

The command guard now refuses thread.archive and thread.delete for a thread of Buddy's project, just as it already refuses archiving, renaming or deleting the project itself. The only exception is thread.delete with onlyIfUnused, so an empty draft can still be cleaned up.

So a Buddy thread is never archived, and a task it delegated to another environment always has its parent in the live shell. The cross-environment traversal from the previous round then hides that task, which its test shows.

  • Every path is covered. Archive and delete reach the server only through dispatch (web, MCP t3_thread_organize, CLI, scheduled tasks), so this holds for all of them. A failed lookup refuses, which fails closed.
  • Nothing else changes. Direct links and ordinary Chat threads are untouched; archiving a Chat thread still works.
  • Tests and docs. The test rows are in managedFolderGuards.test.ts: archive and delete refused, delete-if-unused and a Chat archive allowed. The release contract pins the new guard state (isBuddyThread). The docs replace the stated limitation with this rule.

Why not on the client: keeping archived Buddy parents in the live list atoms would mean subscribing to archive snapshots in the hot list path, and those go stale the moment a parent is archived. Buddy is meant to be one long thread with no archive in its window (R3), so the rule matches the product.

Please review the exact head 10a65501.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes.

Blocking

  • apps/server/src/lazurio/managedFolderGuards.ts:170-180 and apps/server/src/lazurio/managedFolderStartup.ts:64-76: the previous archived-parent finding remains for an existing Buddy project. For example, disable T3CODE_LAZURIO_BUDDY_FOLDER, archive a Buddy thread that has a task in another environment, and enable it again. While disabled, the new guard permits the archive; on restart, bootstrap adopts the existing project without restoring the thread. The live shell still lacks that parent, so unlistedThreadKeys cannot hide its non-archived remote task. Handle existing archived parents when enabling or re-enabling the setting, and test that transition with tag filtering off while preserving direct links.

Non-blocking

The guard prevents new archive and ordinary delete commands while Buddy is configured. Focused tests passed (21), as did the release contract (52). check:changed passed format, lint, knip, GraphQL, typecheck and React compiler; its test stage failed only AgentContextBudget.test.ts, also failing on main as tracked in #167. CI was still running. I did not independently exercise the web client in a browser.

Order and migrations: publish stable 0.1.9-lazurio.1 before merging this PR, as recorded in #214 (comment); the plan's documentation gate must also be complete before implementation proceeds.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Fixed in 3f5e7bb9.

After adopting Buddy's project, the startup now reads that project's archived threads (getShellSnapshot({ location: "archive", projectId })) and dispatches thread.unarchive for each one. So the rule "Buddy's threads are not archived" holds across turning T3CODE_LAZURIO_BUDDY_FOLDER off and on: once the setting is back, the parent is live again. The previous round's cross-environment traversal then hides its remote task, and its existing test shows that with tag filtering off. Direct links are unaffected.

  • Orchestrator in the startup phase. serverRuntimeStartup.ts now gives the phase the orchestrator explicitly. The file was already on the allowlist, and the contract seam on ensureManagedFolderProject still matches.

  • New test. In managedFolderStartup.test.ts, the startup over a project that has an archived Buddy thread and an archived Chat thread unarchives only the Buddy one.

  • Docs state the rule.

  • Release contract: 52 pass.

  • check:changed: everything passes except AgentContextBudget (Agent context budget test fails on current main #167).

  • Not exercised against a live server; this is covered by the unit test only.

Please review the exact head 3f5e7bb9.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes.

Blocking

  • apps/server/src/lazurio/managedFolderStartup.ts:41-49,78-95: the previous archived-parent finding remains when the Buddy folder is missing. For example, disable T3CODE_LAZURIO_BUDDY_FOLDER, archive a Buddy thread with a live delegated task in another environment, remove the folder, and re-enable the setting. The existing project remains unlisted, but the existence check skips ensureBuddyProject and its new unarchive pass; the live shell lacks the archived parent, so the remote task is listed with tag filtering off. Preserve the parent's identity or restore its threads even when the folder is absent, and cover this transition while retaining direct links and ordinary Chat threads.

Non-blocking

The new pass handles an archived Buddy parent when its folder exists. Focused startup and unlisting tests passed (9), as did the release contract (52). check:changed passed format, lint, knip, GraphQL, typecheck and React compiler; its test stage failed only AgentContextBudget.test.ts, also failing on main as tracked in #167. CI was pending. I did not independently exercise the web client in a browser.

Order and migrations: publish stable 0.1.9-lazurio.1 before merging this PR, as recorded in #214 (comment); the plan's documentation gate must also be complete before implementation proceeds.

— Pablo

@immakermatty

Copy link
Copy Markdown
Author

Fixed in acabc249.

The unarchive pass is now its own step (restoreBuddyThreads) and runs in both cases:

  • The folder exists. The startup adopts or creates Buddy's project, then restores its archived threads.
  • The folder is missing. The startup finds the earlier project whose root equals the configured path, which the config keeps for a missing folder, and restores its threads without bootstrapping anything.

With the setting on, a Buddy thread is therefore never archived, whatever happened while it was off. A remote task always has a live parent, and the cross-environment traversal hides that task. Direct links and ordinary Chat threads are unchanged.

New test in managedFolderStartup.test.ts, over one database: start with the folder, start without the setting, remove the folder, start with the setting again. The archived Buddy thread is unarchived. On 3f5e7bb9 this test fails, because the pass was skipped.

Please review the exact head acabc249.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

Blocking: None. The previous finding is addressed: startup restores the existing Buddy project’s archived threads even when the folder is absent.

Non-blocking: Focused startup and unlisting tests passed (10), as did the release contract (52). check:changed passed format, lint, knip, GraphQL, typecheck and React compiler; its test stage failed only AgentContextBudget.test.ts, the existing main failure tracked in #167. CI was still running. I did not independently exercise the web client in a browser.

Order and migrations: publish stable 0.1.9-lazurio.1 before merging this PR, as recorded in #214 (comment); the plan’s documentation gate must also be complete before implementation proceeds.

— Pablo

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: None. The previous findings remain resolved on this head.

Non-blocking: Focused tests passed (35), as did the release contract (52). GitHub CI passed on this head, including server, web browser and client-runtime tests. Locally, check:changed passed format, lint, knip, GraphQL, typecheck and React compiler; its test stage encountered the existing AgentContextBudget failure tracked in #167 and could not launch Chromium because it is absent here. I did not independently exercise the UI in a browser; the PR records the author’s live walkthrough.

Order and migrations: publish stable v0.1.9-lazurio.1 before merging this PR, then merge #216, as recorded in #214 (comment). The first R1 pilot thread must verify its instructions, skills and MCP before R2, per LZD-0033.

— Pablo

@immakermatty
immakermatty merged commit 83cb079 into main Nov 17, 2026
8 checks passed
@immakermatty
immakermatty deleted the lazurio/buddy-project-beside-folder branch November 17, 2026 23:52
@immakermatty

Copy link
Copy Markdown
Author

Supervisor: the merged change is read, and the earlier findings are fixed. (2026-11-18)

main moved 388b772e → 83cb079f (this PR, approved by the persona on its exact head f542b6c9 at 23:47:39 UTC). Read acabc249..f542b6c9 (15 files, +147/−45). The should-fix findings are fixed:

  • notifications read listHiddenThreadKeysAtom (ThreadNotificationCoordinator.tsx:93, 125, 415);
  • useHiddenThreadKeys() now returns the list-hidden set, which covers the palette and the relationships panel, and the palette also applies listedLinkedRows;
  • Buddy's startup part is wrapped in Effect.catchCause + logWarning, so Chat starts without it.

Also fixed: an archived Buddy project is unarchived on adoption (archived: false), and useActiveProjectTarget was reworked. I found no new defect. Next: #216 after a fresh review on its exact head, then the 0.1.9-lazurio.2 preview from the tip of main.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812

immakermatty added a commit that referenced this pull request Nov 18, 2026
…ght panel across the whole width (#216)

Narrow window: the rail only inside the open left panel (reachable by keyboard and screen readers, its jump visible and typable while it is hidden), the right panel across the whole width. CSS and a short script in index.html's shell slot; browser test narrowRail.browser.test.tsx, contract test, runbook. For 0.1.9-lazurio.2 together with #214, after v0.1.9-lazurio.1. Review: Pablo APPROVED on ae9d237 at 00:06:16 UTC, after the last commit; checks green.

Merged under the night mandate of 2026-11-17, read by the coordinating thread at 21:28 UTC, verbatim: "Dávám ti plný mandát pracovat na tom, o čem jsme se dneska bavili, a dotáhnout to do konce. Udělat zápisy, cleanup, releasy, publikování."

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
…y the server and unlisted in Chat

T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder beside the managed
Folder. The startup adopts or creates its project (Buddy); create from any
client, agent or CLI still refuses it, and nothing renames, archives or
removes it or its threads. Threads, messages, forks and agent turns run in
its root as in the Folder's. A folder not made yet leaves Chat running
without the project. The web leaves the project and its threads (with their
tasks in other Environments) out of every list, search, archive and pull
request row, and opens a thread by its link. Unset, nothing changes.

On v0.1.10 upstream rewrote ThreadNotificationCoordinator.tsx (toasts
close through closeToasts, a snoozed gate, an opened thread's toasts close
when its route resolves), so its three reads of hidden threads are placed
by hand: closeHiddenPending closes the toasts and system notifications of
list-hidden threads, and present() checks listHiddenThreadKeysAtom before
any sound, toast or notification. The distribution's contract test pins
all three.

Plan LZD-0033 (pilot R1). #214.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
…y the server and unlisted in Chat

T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder beside the managed
Folder. The startup adopts or creates its project (Buddy); create from any
client, agent or CLI still refuses it, and nothing renames, archives or
removes it or its threads. Threads, messages, forks and agent turns run in
its root as in the Folder's. A folder not made yet leaves Chat running
without the project. The web leaves the project and its threads (with their
tasks in other Environments) out of every list, search, archive and pull
request row, and opens a thread by its link. Unset, nothing changes.

On v0.1.10 upstream rewrote ThreadNotificationCoordinator.tsx (toasts
close through closeToasts, a snoozed gate, an opened thread's toasts close
when its route resolves), so its three reads of hidden threads are placed
by hand: closeHiddenPending closes the toasts and system notifications of
list-hidden threads, and present() checks listHiddenThreadKeysAtom before
any sound, toast or notification. The distribution's contract test pins
all three.

Plan LZD-0033 (pilot R1). #214.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
…y the server and unlisted in Chat

T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder beside the managed
Folder. The startup adopts or creates its project (Buddy); create from any
client, agent or CLI still refuses it, and nothing renames, archives or
removes it or its threads. Threads, messages, forks and agent turns run in
its root as in the Folder's. A folder not made yet leaves Chat running
without the project. The web leaves the project and its threads (with their
tasks in other Environments) out of every list, search, archive and pull
request row, and opens a thread by its link. Unset, nothing changes.

On v0.1.10 upstream rewrote ThreadNotificationCoordinator.tsx (toasts
close through closeToasts, a snoozed gate, an opened thread's toasts close
when its route resolves), so its three reads of hidden threads are placed
by hand: closeHiddenPending closes the toasts and system notifications of
list-hidden threads, and present() checks listHiddenThreadKeysAtom before
any sound, toast or notification. The distribution's contract test pins
all three.

Plan LZD-0033 (pilot R1). #214.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
…y the server and unlisted in Chat

T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder beside the managed
Folder. The startup adopts or creates its project (Buddy); create from any
client, agent or CLI still refuses it, and nothing renames, archives or
removes it or its threads. Threads, messages, forks and agent turns run in
its root as in the Folder's. A folder not made yet leaves Chat running
without the project. The web leaves the project and its threads (with their
tasks in other Environments) out of every list, search, archive and pull
request row, and opens a thread by its link. Unset, nothing changes.

On v0.1.10 upstream rewrote ThreadNotificationCoordinator.tsx (toasts
close through closeToasts, a snoozed gate, an opened thread's toasts close
when its route resolves), so its three reads of hidden threads are placed
by hand: closeHiddenPending closes the toasts and system notifications of
list-hidden threads, and present() checks listHiddenThreadKeysAtom before
any sound, toast or notification. The distribution's contract test pins
all three.

Plan LZD-0033 (pilot R1). #214.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
…y the server and unlisted in Chat

T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder beside the managed
Folder. The startup adopts or creates its project (Buddy); create from any
client, agent or CLI still refuses it, and nothing renames, archives or
removes it or its threads. Threads, messages, forks and agent turns run in
its root as in the Folder's. A folder not made yet leaves Chat running
without the project. The web leaves the project and its threads (with their
tasks in other Environments) out of every list, search, archive and pull
request row, and opens a thread by its link. Unset, nothing changes.

On v0.1.10 upstream rewrote ThreadNotificationCoordinator.tsx (toasts
close through closeToasts, a snoozed gate, an opened thread's toasts close
when its route resolves), so its three reads of hidden threads are placed
by hand: closeHiddenPending closes the toasts and system notifications of
list-hidden threads, and present() checks listHiddenThreadKeysAtom before
any sound, toast or notification. The distribution's contract test pins
all three.

Plan LZD-0033 (pilot R1). #214.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check. After the review on c5cf16b, each keyed send claims
  its key before it sends and only the claim's holder sends, so the wait
  T3 keeps is the accepted send's; the runbook describes the claim, the
  send_in_progress refusal, CLAIM_TTL_MS and the limits, and the
  contract test pins the claim, the refusal, the release, the expiry and
  the receipt gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
…y the server and unlisted in Chat

T3CODE_LAZURIO_BUDDY_FOLDER declares Buddy's folder beside the managed
Folder. The startup adopts or creates its project (Buddy); create from any
client, agent or CLI still refuses it, and nothing renames, archives or
removes it or its threads. Threads, messages, forks and agent turns run in
its root as in the Folder's. A folder not made yet leaves Chat running
without the project. The web leaves the project and its threads (with their
tasks in other Environments) out of every list, search, archive and pull
request row, and opens a thread by its link. Unset, nothing changes.

On v0.1.10 upstream rewrote ThreadNotificationCoordinator.tsx (toasts
close through closeToasts, a snoozed gate, an opened thread's toasts close
when its route resolves), so its three reads of hidden threads are placed
by hand: closeHiddenPending closes the toasts and system notifications of
list-hidden threads, and present() checks listHiddenThreadKeysAtom before
any sound, toast or notification. The distribution's contract test pins
all three.

Plan LZD-0033 (pilot R1). #214.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
immakermatty added a commit that referenced this pull request Nov 18, 2026
The distribution's files on the new base, upstream T3 Code v0.1.10
(7d32075), last in the stack: CI,
the CLI archive, release and upstream watch workflows, the image, the
issue form, README, SECURITY.md, the runbook, the overlay spec, the
contract test, the release version check and the rebuild's skill. They
are main's files, made current for v0.1.10 (#213). Main's
base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9
below are kept from the earlier rebuilds.

On v0.1.4:

- The allowlist gains five files: chat/ThreadServersPanel.tsx, where a
  click on a thread's server opens it in the Environment browser (row 9);
  sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts,
  for the per-server target and the continuation gate of v0.1.4's update
  dialog (row 4); upstream's installer test install.test.ts, whose fixture
  needs upstream's repository named (row 4); and cli/environment.ts, whose
  settings take Buddy's linked-Environments guard (row 25).
  ServerEnvironment.test.ts keeps the update-check guard (row 4).
- The contract test's pins follow the seams that moved: upstream deleted
  LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column
  head is pinned in the thread sidebar only; the sidebar reads
  useDelegatedUnderParent before the managed check; the empty panel and
  Nová karta carry the workspace focus default; the MCP session issue
  calls mcpClientScopes directly; an agent command's scope drops the
  session's web origin so its thread links stay t3-thread:// links; the
  Buddy composer hook takes only the environment, since v0.1.4's resting
  composer has no strip of its own; the timeline has no paint-only gate
  (pingdotgg#25787); the steer guard returns through
  stopRunForQueuedCommand and also holds a delegated task's completion
  wake; the Servers panel's click opens the Environment browser; and
  Buddy's server settings layer turns linked Environments off.
- Rows 30, 32 and 33, which main carried as commits after row 31, now
  sit in their rows; row 28's addenda are back in rows 7, 23 and 25.
  Upstream renamed the lint rule react-effect-budget to
  t3code/no-unreasoned-state-sync (pingdotgg#26161).
- The skill's inventory groups cover rows 23 to 33.
- Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name
  only fictional people and hosts (Alena, Bob, example-person,
  vm-0x.example.lazurio.io), since the repository is public.

On v0.1.5:

- CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the
  issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm
  12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy.
- The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets
  t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so
  lazurio-cli-archives.yml installs patchelf before the build, the way
  upstream's release-desktop.yml does; the contract test pins the order.
- useUpdateEverything.ts leaves the allowlist: row 4 now keeps a
  server's advertised release out of waitForNpm in
  updateEverything.logic.ts (pingdotgg#26917), and the contract
  test pins that seam there. The fixed test gate is unchanged, and every
  gated path exists at v0.1.5.
- The contract test's pairing pins follow the constants that knip made
  module-private (upstream's pre-commit hook runs knip:check since
  pingdotgg#26167).
- The runbook's Overlay table describes every row on v0.1.5, the Cílový
  stack names each row's new commit, the swap step names the workflows
  to disable after the swap from the v0.1.3 base (agent-context-budget.yml,
  mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the
  skill say to replay with --no-verify and run knip over the finished
  stack.

On v0.1.6:

- CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the
  issue form's version example is 0.1.6-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
- The allowlist is unchanged. Its comments say why ServerEnvironment.ts
  and server.ts offer and build no triage on a Lazurio Environment
  (row 15, #147), why ws.ts runs no ChatGPT handoff there
  and the web starts none through a Lazurio primary (row 18,
  #145), that useComposerSend.ts counts a prompt toward
  upstream's star request (pingdotgg#27832) only outside a Lazurio
  Environment (row 16), and that no update waits on npm since
  pingdotgg#27847 (row 4).
- The contract test pins those seams: the triage guard and its one
  construction, the star prompt's check and its one call, the handoff
  route, reconnectProfile and the web's routing, and on Buddy's surface
  the inline mask over useThreadLifecycle's attentionNow and workNow,
  every line of it (React Compiler, #135), the items'
  counts in useThreadLifecycle.tsx and its one caller, the promise
  ChatView hands Nová karta for a side chat (row 13), and that Buddy's
  surface offers no side chat (row 25). It also follows
  the seams upstream moved: no waitForNpm left in the update dialog's
  logic, the palette's addProjectAction, the sidebar's pickable project
  groups (pingdotgg#26154), and an embedded side chat
  (pingdotgg#26901) without thread tabs, terminal drawers or the
  right panel. Claude's mcp-elicitation requests and the agent scope's
  kill are covered by rows 30 and 8's own tests.
- The runbook's Overlay table describes every row on v0.1.6, the Cílový
  stack names each row's new commit and the files rows 13, 15, 16 and 18
  now change, and the swap step adds mobile-eas-preview-fork.yml to the
  workflows to disable after the swap. The runbook and the skill say to
  address a fix written over the finished stack to the row that added
  the place it changes.

On v0.1.7:

- CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the
  issue form's version example is 0.1.7-lazurio.1. The toolchain pins
  hold, and SECURITY.md's upstream section equals the new tag's policy.
  v0.1.7 adds no workflow, so the swap step's list is unchanged.
- The allowlist gains toolkits/preview/handlers.ts and its test: since
  v0.1.7 preview_open takes a dev-server target (pingdotgg#28027),
  and upstream's handler answered an open with a target with the
  navigate result alone; row 10 keeps the open answer underneath, so the
  Environment browser's view stays. The fixed test gate is unchanged.
- The contract test follows the seams that moved: the settings writer
  takes the client's patch for the managed policy
  (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime
  notes come from the active session setup, the MCP caller's webOrigin
  is now hostedAppUrl, the steer guard's waitsOnPendingRequest also
  holds a delegated task's question (pingdotgg#29909), and the
  ACP adapter filters T3's options through a flatMap.
- For row 30 the allowlist gains apps/web's components/ChatView.logic.ts
  and its test and components/chat/composerCommandKey.ts,
  client-runtime's state/composerDispatch.ts and its test, and
  contracts' orchestrationV2.ts: eight files with the two above. The
  contract test pins that the web keeps auto input auto while the run is
  set up; that /compact and /logout wait for no turn; that a running
  update takes the thread lock on its provider turn's first report or
  while a follow-up waits, then checks again under the lock; and that
  each follow-up gets one promotion, so a held one, one already promoted
  and a refused one stay queued without holding back the next.
- Stage 3's checkout command names the release version check's script
  and test (#165), which the v0.1.6 runbook left out.
- The runbook's Overlay table describes every row on v0.1.7, and the
  Cílový stack names each row's new commit. Main's Cílový stack still
  named older hashes from row 10 on, so the runbook and the skill now say
  to take each row's commit from main's log by subject. The runbook also
  records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices,
  ManagedPolicy.layerTest()) and that the overlay's settings writes go
  through updateSettingsWith, so the managed policy vets them.
- The runbook records what the independent check of this rebuild found:
  Codex 0.166.0, T3's managed runtime since v0.1.7, still has
  default_mode_request_user_input off by default (row 22); mcp-client
  sessions get hosted thread links on the external origin (row 20);
  upstream's star prompt now stars through the Environment's account
  (row 16); the policy lock reads the macOS and Windows sources too
  (row 18); two upstream policy paths in the update flow do not follow
  row 4's target and are offered upstream; row 30's refused promotion,
  /goal and cold-start steer; and row 33's steer page block. The overlay
  CLI tests build auth on the test managed policy.

On v0.1.8:

- CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the
  issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's
  upstream section equals the new tag's policy, whose contact is now
  security@t3.codes.
- The allowlist is unchanged. v0.1.8 adds no workflow, so the swap
  step's list is unchanged. Upstream's release-desktop.yml can now defer
  the macOS CLI's notarization with --notary-submission-file;
  lazurio-cli-archives.yml signs ad hoc, passes no such file and is
  unchanged.
- The contract test follows the seams that moved: the sidebar control
  takes showSidebar; the composer controls bar's hooks end with the
  model pick (pingdotgg#31739) and Buddy's controls return after
  them; an offered prompt suggestion comes before Buddy's placeholder
  (pingdotgg#28047); and a fresh session after /clear
  (pingdotgg#30325) never steers, in the web's dispatch mode and
  in the server's steer and promotion guards. Two new pins keep the
  Buddy surface's hides of upstream's new entries: "Use in another app"
  (decision A8) and /clear's fresh session (decision A7).
- The runbook's Overlay table describes every row on v0.1.8, the Cílový
  stack names each row's new commit and files (viewAddressCases.ts in
  rows 9 and 10), and row 30's text no longer compares
  waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending
  user_input. The runbook records this rebuild's conflicts and that a
  test the rebuild adds belongs in the row's own test file or under
  apps/*/src/lazurio/, since an upstream test file off the allowlist
  fails fork CI.

On v0.1.9:

- CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the
  issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and
  pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left
  SECURITY.md unchanged, so its upstream section still equals the tag's
  policy.
- The allowlist is unchanged. The contract test's seams are unchanged
  apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate
  (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name
  their adaptations in their own messages.
- v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its
  own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in
  pingdotgg/t3code, and the swap step adds it to the workflows to
  disable after the swap. The changed ci.yml and four mobile workflows
  stay disabled.
- The runbook's Overlay table describes every row on v0.1.9, the
  Cílový stack names each row's new commit, and the runbook records
  this rebuild's conflicts and decisions. Upstream's new screen reader
  announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's
  surface, so a screen reader never hears T3's steps there (row 28);
  the contract test pins that cap in MessagesTimeline.tsx.

On v0.1.10:

- CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the
  issue form's version example is 0.1.10-lazurio.1. Upstream moved to
  Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the
  image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest.
  Upstream left SECURITY.md unchanged, so its upstream section still
  equals the tag's policy; this row adds the fork's section to it.
- The allowlist drops branding.ts, ChatView.logic.ts and its test,
  composerCommandKey.ts and composerDispatch.ts and its test, which the
  overlay no longer changes: upstream now picks the stage label in
  branding.logic.ts, and it steers a follow-up sent before the provider
  turn started (pingdotgg#34581). Row 30 now turns an auto send
  made then into that deferred steer in Orchestrator.ts and marks it
  automatic on the queued run, so orchestrationV2.ts stays
  (#170). It adds sidebar/updateEverythingRun.tsx and its
  test, where row 4's Retry compares a Lazurio release's whole version,
  and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry
  row 4's per-row target; main.test.ts, whose stand-in window carries
  the address the prompt link capture reads (row 6); and binCli.test.ts,
  which reads row 21's `t3 thread list --json` with its total. The guard
  passes both ways on the candidate.
- The contract test follows the seams upstream moved: the launcher path
  now comes from cloud/pinnedRuntime.ts, the build stamps the page title
  from the stage label (pingdotgg#18442, and no release workflow
  sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag
  (sendRuntimeInstructions), the ACP adapter also resets unset options
  (pingdotgg#35199, held back on Buddy's instance too), provider
  hydration reads the database config (pingdotgg#34877), a
  natively resumed thread sends its unsent message
  (pingdotgg#36526), a failed send gives back the snapshot's
  draftText (pingdotgg#33124), a linked Environment's sender names
  it (pingdotgg#34721), an expandable work row's chevron sits
  between the acting-sender mark and the time (pingdotgg#35549),
  and the collapsed composer previews the prompt (pingdotgg#22148).
  Row 30's checks now pin that the one promote-to-steer is upstream's
  deferred steer, behind the pending-request guard that clears its
  steerWhenReadyRunId and steerWhenReadyIntent; the conditions under
  which an auto send in the gap becomes that steer, through
  resolveMessageDispatchIntent and the adapter's steering or
  interrupt-and-restart; and the delivery check that lets such a steer in
  only where the policy steers it then, by the session's capabilities.
- v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and
  pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC;
  it labels, comments on and closes pull requests, dry-run without
  PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the
  swap step disables them right after the swap. The swap push itself
  starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so
  the step first cancels that run and then removes any vouch label it
  gave an open issue.
- The Overlay table gains rows 35 to 37 for #214 and #216, and the
  Cílový stack names their commits on main and their files. Rows 4, 15,
  21 and 30 record the fixes from the candidate's independent check
  (#222); the rest of the table is brought up to v0.1.10
  after the release (stage 9). The runbook's "Z přestavby na v0.1.10"
  records the conflicts, the hand adaptations and those fixes, numbering
  rows as the table does, and names the replayed main (faae02a, stable
  0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216).
- Main's #214, #216 and #220 additions to CI, the contract test and the
  runbook are carried unchanged; #216's narrow-rail pin follows row 36's
  `hidden` adaptation. A new contract pin holds row 35's hand-placed
  coordinator change: ThreadNotificationCoordinator.tsx reads hidden
  threads three times, always as listHiddenThreadKeysAtom, so Buddy's
  project's threads never sound, toast or notify.
- The review of the candidate at 50a5004 (#222) adds to
  the runbook: the contract inventory names orchestrationV2.ts with
  steerWhenReadyIntent only; rows 24 and 30 record the recorded
  followWakes and the auto steer that a question puts first in the
  queue; the F50 gate names holders.vectors.test.ts and the vendored
  Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the
  new version reads both forms of the launcher, a symlink and since
  v0.1.10 the script posixLauncherScript writes; and the update channel
  and its procedure describe the launcher protocol's move from 3 to 4,
  which an Update from 0.1.9 passes while the 0.1.9 launcher stays until
  a local update or service install restarts the service. The contract
  test pins the copied release and the vectors' runner. After the next
  review row 24 records the wait before the send, so a repeat racing the
  first send cannot record its own; the runbook says so and drops the
  crash between send and record from the known limits. After the review
  after that, T3 records the wait only until it accepts the key's command
  and each send reads the last record after it sent, so a send that
  fails between record and dispatch leaves no wait a retry follows; the
  contract test pins the record before the send, the read after it and
  the receipt check. After the review on c5cf16b, each keyed send claims
  its key before it sends and only the claim's holder sends, so the wait
  T3 keeps is the accepted send's; the runbook describes the claim, the
  send_in_progress refusal, CLAIM_TTL_MS and the limits, and the
  contract test pins the claim, the refusal, the release, the expiry and
the receipt gate. After the review on 7b12202, only a send T3 refused
before dispatching it releases its claim (UNSENT_FAILURES), and any
other failure, such as a lost answer, keeps it until T3 accepts the
command or CLAIM_TTL_MS passes; the runbook says so in the send-state
paragraph and its limits, and the contract test pins the exact set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants